fix: correct export name in TypeScript tool template generation#83
Merged
jmhbh merged 1 commit intoSep 12, 2025
Merged
Conversation
Signed-off-by: Anurag Ojha <aojharaj2004@gmail.com>
intojhanurag
force-pushed
the
fix/typescript-tool-export-name
branch
from
634c31d to
d1a4d55
Compare
Contributor
Author
|
Hey @rinormaloku , this Pr is ready for review |
peterj
approved these changes
Sep 12, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
fix: #81
The template now uses {{.ToolNameCamelCase}} for the exported symbol.
Generated tools match the import name automatically.
Running npm run dev after adding a new tool works without modification.
Before:
After:
